-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ADP-2102] Remove mentions of stack
from documentation and code
#3671
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Some minor suggestions.
@@ -20,7 +20,7 @@ | |||
# individually. For example, run step1 to set up a state directory for | |||
# the old version, then try: | |||
# stateDir=./debug /nix/store/...-launch-migration-test-v2019-12-16.sh step1 | |||
# stack exec migration-test -- step2 launch --state-dir=./debug ... | |||
# exec migration-test -- step2 launch --state-dir=./debug ... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps:
# exec migration-test -- step2 launch --state-dir=./debug ... | |
# cabal run migration-test -- step2 launch --state-dir=./debug ... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
… except that we do not have a migration-test
component in any of our .cabal files. 😅 It appears that these tests for database migration have never been ported to the Shelley era and are completely broken.
Fixing the database migration tests is out of scope for this pull request, so I would prefer to write something blatantly wrong rather than try to pretend that the command cabal run migration-test
may have worked at some point.
Co-authored-by: Jonathan Knowles <[email protected]>
bors merge |
Build succeeded: |
…cumentation and code r=HeinrichApfelmus a=HeinrichApfelmus ### Overview This pull request removes all substantial mentions of `stack` from the documentation and .nix code. This includes LICENSE README.md bors.toml cabal.project default.nix docker-compose.yml docs flake.lock flake.nix floskell.json hie-direnv.yaml lib nix prototypes reports scripts shell.nix specifications test touch.me.CI weeder.dhall Mentions of `stack2cabal.nix`. LICENSE README.md bors.toml cabal.project default.nix docker-compose.yml docs flake.lock flake.nix floskell.json hie-direnv.yaml lib nix prototypes reports scripts shell.nix specifications test touch.me.CI weeder.dhall Nix shells for use with `stack`. LICENSE README.md bors.toml cabal.project default.nix docker-compose.yml docs flake.lock flake.nix floskell.json hie-direnv.yaml lib nix prototypes reports scripts shell.nix specifications test touch.me.CI weeder.dhall Mentions of `stack.yaml` as canonical source of package dependencies. ### Comments LICENSE README.md bors.toml cabal.project default.nix docker-compose.yml docs flake.lock flake.nix floskell.json hie-direnv.yaml lib nix prototypes reports scripts shell.nix specifications test touch.me.CI weeder.dhall Searching for the string `stack` in the project folder no longer turns up substantial results. ### Issue Number ADP-2102 Co-authored-by: Heinrich Apfelmus <[email protected]> Source commit: e2749fb
Overview
This pull request removes all substantial mentions of
stack
from the documentation and .nix code. This includesstack2cabal.nix
.stack
.stack.yaml
as canonical source of package dependencies.Comments
stack
in the project folder no longer turns up substantial results.Issue Number
ADP-2102